-
-
Notifications
You must be signed in to change notification settings - Fork 565
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: downgrade dependencies to avoid 500 error on /oauth/callback
#3075
Conversation
✅ Deploy Preview for elk-docs canceled.
|
✅ Deploy Preview for elk-zone ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected], npm/[email protected] |
OK, the 500 error has disappeared now. Some of those updates should be causing the error, so we can narrow down the suspect by updating those packages little by little. |
/oauth/callback
…rade-nuxt # Conflicts: # package.json # pnpm-lock.yaml
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. |
…rade-nuxt # Conflicts: # package.json # pnpm-lock.yaml
The above commits with passed CI (✅) had no issue including chore: update nuxt-component-meta and unstorage in resolutions (90aa666) but chore: update nuxt and @nuxt/schema (b3c961e) introduced the 500 error again. So there's some issue between the previous nuxt v3.13.2 and v3.14.1592. |
69cc79b
to
32e1908
Compare
nuxt>=3.14.0 doesn't work. I think we can merge this with the previous version of nuxt (v3.13.2) until we can figure out the root cause so that users can sign in on main.elk.zone again. This might be related to |
What's the server error? |
I can see only 500 error on Netlify preview. We need Netlify's server log to check the actually error. |
…rade-nuxt # Conflicts: # package.json # pnpm-lock.yaml
I'd like to merge this since it also occurs on other endpoints and blocks the other PR previews (e.g. #3033). Examples:
We can investigate the root cause when we upgrade back to nuxt>=3.14.0 again in a separate PR. |
fix #3072
I bisect the past Netlify previews and it seems that the 500 error starts after merging #3046. Downgrading nuxt might fix the 500 error on
/oauth/callback
after log-in.This is only a temporary workaround and I haven't found the root cause of 500 error.